@baszalmstra Because we need to update the dependencies directly in file to allow for correct solving of the PyPI environment when it is used as a path = "." dependency. But I have a strong feeling we should find a way we should get rid of this. But the current behavior is really broken, so this is a workaround. If you have better ideas, please share.

This also doesn't work with interrupting the add process ...

The context is that we need to save the pyproject.toml during upgrading or adding, since changes to project.dependencies need to be available to uv.

If we save, we also need to save in order to revert the change if things go wrong.

Can we only do it for that specific case then?

can we pass pyproject.toml from a tmp location to uv? or maybe uv can read it from stdin? this case we don't need to save it back on disk to the original location
cc @tdejager

@nichmor that would not work for relative path dependencies?

@nichmor that would not work for relative path dependencies?

could we change it to absolute during resolving/building?

@nichmor I'm kinda unsure how this solves anyhing, as we are not letting uv read the pyproject.toml in most cases only since we pass in project.dependencies programatically anyways, but I've not dived in to the issue yet :)

I changed the logic so that we only intermediary save when the manifest is a pyproject.toml. And then always revert the manifest on a dry-run.